System and method for adding routing paths in a network

ABSTRACT

Aspects of the present disclosure involve systems, methods, computer program products, and the like, for generating a routing table. In one implementation, BGP route broadcasts are received by a control plane of a network. The BGP route broadcasts are aggregated into a table of address summarized routes based on IP addresses included in the BGP route broadcasts. A table of attribute summarized routes is generated from the table of address summarized routes based on similarities between attributes included in the address summarized routes.

TECHNICAL FIELD

Embodiments of the present invention generally relate to systems andmethods for implementing a telecommunications network, and morespecifically for generating routing tables for a telecommunicationsnetwork.

BACKGROUND

Network traffic is typically managed by routers that forward datapackets through the network according to routing tables received andmaintained by a control plane. Routing tables often include hundreds ofthousands or millions of entries denoting routing paths through thenetwork for traffic directed to particular addresses. Many routers areunable to directly store large routing tables. In some cases, redundantdevices are used to address space limitations. In other cases, expandedmemory components may be used, but that can slow traffic forwarding dueto requiring more complicated routing table lookup procedures. However,if table size could be reduced while allowing for correct forwarding ofnetwork traffic, the need for redundant devices or expanded memorycomponents may be lessened.

It is with these observations in mind, among others, that aspects of thepresent disclosure were concerned and developed.

SUMMARY

In a first embodiment of the invention, a method for generating arouting table includes receiving multiple routing informationbroadcasts, the routing information broadcasts including an InternetProtocol (IP) address, a mask value, and metadata, generating an addresssummarized table by comparing IP addresses and mask values between themultiple routing information broadcasts, the address summarized tableincluding contiguous IP address and corresponding mask values, andgenerating an attribute summarized table by comparing metadata betweenaddress summarized table entries, the attribute summarized tableincluding address summarized table entries having identical portions ofmetadata.

In one embodiment, the metadata comprises one of a local preference, anautonomous system (AS) path length, an AS path, or a multiple exitdiscriminator (MED).

In one embodiment, the method further includes forwarding a packet basedthrough a network on the attribute summarized table.

In one embodiment, the routing information broadcasts comprises one ormore border gateway protocol (BGP) broadcasts.

In one embodiment, the BGP broadcasts are received by one or more routereflectors comprising a data plane for a network.

In one embodiment, a route reflector receives the routing informationbroadcasts, and the method includes storing the attribute summarizedtable on a router.

In one embodiment, multiple routers store respective copies of theattribute summarized table, each respective copy of the attributesummarized table including interface identifiers for forwarding packetsacross a network.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram illustrating an exemplary InternetProtocol (IP) operating environment, in accordance with one embodimentof the present disclosure, in accordance with various embodiments of thepresent technology;

FIG. 2 is a schematic diagram illustrating a network environment toprovide multiple routes to a client network through the networkenvironment, in accordance with various embodiments of the presenttechnology;

FIG. 3 is a flowchart illustrating a method for populating a routingtable with summarized IP addresses, in accordance with variousembodiments of the present technology;

FIG. 4 is a diagram illustrating summarized routing tables, inaccordance with various embodiments of the present technology; and

FIG. 5 is a diagram illustrating an example of a computing system whichmay be used in implementing various embodiments of the presentdisclosure.

DETAILED DESCRIPTION

Aspects of the present disclosure involve systems, methods, computerprogram products, and the like, for generating a routing table ofsummarized IP addresses in a telecommunications network. In general, theprocess allows for addresses intended for a routing table to be groupedbased on similarities between the addresses themselves as well asbetween metadata associated with each address. More particularly, acontrol plane of a network is able to receive border gateway protocol(BGP) routes, in the form of IP addresses coupled to metadata. Further,the control plane may summarize the received routes and place them in arouting table according to the combined address and metadata groupings.The routing table may be used by the control plane to orchestrateforwarding packets directed to the summarized IP addresses by routersand other components within the network. By summarizing the addressesusing the IP address information as well as the metadata, routing tablesmaintained within the network can be greatly reduced in size. In somecases, the reduced size of the routing table may allow routers or othercomponents to maintain the entirety of the table in memory where theywould otherwise be unable to fit a functional routing table due to spacelimitations.

FIG. 1 illustrates an example of an operating environment 100 for atelecommunications network receiving BGP routes from client devices ofthe network and utilizing those routes to transfer data through thetelecommunications from one network terminus to another. In general, theenvironment 100 provides for establishing communication sessions betweennetwork user devices (e.g., computers, smartphones, mobile devices,tablets, etc.) and for providing one or more network services to networkuser devices. As depicted in FIG. 1 , the environment 100 includes an IPnetwork 102, which may be provided by a wholesale network serviceprovider. In some examples, portions of the network may include non-IPbased routing in addition to, or instead of, the IP network 102. Ingeneral, the network 102 of FIG. 1 may include any communication networkdevices known or hereafter developed.

The IP network 102 includes various components such as, without imputinglimitation, gateways, routers, registrars, and abstraction layers suchas control planes and data planes, and the like which will be readilyunderstood to be included by a person having ordinary skill in the art.With specific reference to FIG. 1 , the IP network 102 includes multiplerouters 105 for internally managing network traffic between networkendpoints. A packet received by the network will be forwarded from onerouter 105 to another router 105 according to a pre-determined routingtable. The routing table provides forwarding information for each router105 and is stored by each router 105 in memory. The routing table of agiven router 105 allows the router 105 to identify, based on thedestination of a received packet, to which next router 105 to forwardthe received packet along a transmission route through the network. Insome examples, the router table can take up the significant majority orall of the storage memory of a router 105.

A customer network 112 can include various communications devices suchas, without imputing limitation, routers, personal computers,telephones, and the like, as will be apparent to a person havingordinary skill in the art. As such, although discussed herein aspertaining to “routers”, it should be appreciated that the methods andsystems described may also apply to the other components of the network.The customer network 112 can connect to the IP network 102 through acustomer gateway 108. The customer gateway 108 can be, without imputinglimitation, any or multiple of various communications devices such as amodem, a secondary network, a network bridge, and the like. The customergateway 108 will enable a customer network 112 to communicate withanother customer network 112, such as a border network 114 including acustomer home or local area network (LAN) 118, or the Internet 110.Communications sent from the customer network 112 may traverse, or routethrough, the IP network 105 via forwarding between the routers 105. Forexample, as depicted in FIG. 1 , communications from the customernetwork 112 to the Internet 110 can route through the routers 105according to the dashed line connecting the customer gateway 108 to aprovider edge 104 across the said routers.

The customer home or LAN 118 may include communications device 120 and ahome router 116. Although depicted here as a computer, thecommunications device 120 can be any type of communications devices thatreceives a multimedia signal, such as an audio, video, or web-basedsignal, and presents that signal for use by a user of the communicationsdevice. For example, the customer home or LAN 118 can include asmartphone, tablet, edge device, and the like. The home router 116 maymanage and/or facilitate communications between the customer home or LAN118 and other devices over the IP network 102, such as the customernetwork 112 and/or the Internet 110.

The customer home or LAN 118 typically connects to the IP network 102via a border network 114, such as one provided by an Internet ServiceProvider (ISP). The border network 114 is typically provided andmaintained by a business or organization such as a local telephonecompany or cable company. The border network 114 can provide network andcommunications related services to their customers. In contrast, thecustomer gateway 108 accesses the IP network 102 directly. Communicationvia any of the networks can be wired, wireless, or a combination of thetwo. Additionally, the border network 114 may connect to the Internet110 through a provider edge 106, 104.

As mentioned above, the telecommunications network may allow a customerto connect to the network through a provider edge 132. In someinstances, a customer network may connect to the telecommunicationsnetwork through more than one provider edge device. In particular, FIG.2 is a schematic diagram illustrating a network environment 200including multiple routes for a border network 204, 226 through thenetwork environment. The telecommunications network 202 of FIG. 2 may besimilar to that of FIG. 1 such that the networks may include the same orsimilar components. Further, border networks 204, 226 connected to thetelecommunications network 202 can utilize the network to send andreceive packets of information to/from other border networks, clientnetworks, and/or other connected networks such as client networks,provider networks, and the like.

As shown in FIG. 2 , a border network 204 includes a provider edge A 206and provider edge B 208. The border network 204 connects to the network202 through the provider edge A 206 and the provider edge B 208. Wherethe border network 204 connects through provider edge A 206, areciprocal provider edge C 210 of the network 202 may complete theconnection. Likewise, where the border network 204 connects to thenetwork 202 through provider edge B 208, a reciprocal provider edge D212 of the network 202 may complete the connection. While the provideredges are depicted here connecting through individual reciprocatingprovider edges, it is understood that two or more provider edges mayconnect to the network 202 through a single counterpart provider edgeand that, likewise, a single provider edge may connect to the network202 through multiple counterpart provider edges of the network 202.

The network 202 can include a control plane 214 which may communicatewith provider edges C-F 210, 212, 218, 220 of the network 202. Thecontrol plane 214 can determine routing and data flow policies whichwill be carried out by routers 205 of the network 202. The control plane214 can broadcast the policies out to routers 205 via a route reflector228 included in the control plane 214. In one particular embodiment, thecontrol plane 214 may also generate a routing table and the like. Theroute reflector 228 may communicate with some or all of the routers 205in order to distribute the generated routing table. The control plane214 can include various software and hardware interfaces, communicationsdevices, and other elements as will be apparent to a person havingordinary skill in the art.

The control plane 214 may receive routing information in the form ofBorder Gateway Protocol (“BGP”) route broadcasts from provider edges C-F210, 212, 218, 220 of the network 202. The provider edges C-F 210, 212,218, 220 may in turn have received the BGP route broadcast fromassociated provider edges A 206, B 208, G 222, and H 224. In oneparticular configuration, the control plane 214 may relay the receivedBGP route broadcasts to the route reflector 228 for entry into therouting table. Once the route reflector 228 has generated or updated therouting table, the route reflector 214 may broadcast the new routingtable to one or more of the routers 205.

Although a single route reflector 228 is depicted within the controlplane 214, it is understood that the control plane 214 can includemultiple route reflectors and/or other devices for drawing and managinga topology of the network 202, as will be apparent to a person havingordinary skill in the art. For example, specialized devices along withmultiple route reflectors can make up a control plane in order toprovide redundant, and thus fault tolerant, dissemination of routingtables and/or dynamic traffic shaping based on routing tables andreal-time traffic loads across the network 202.

In one example, the router reflector 228 may generate the routing tableaccording to a method 300 depicted by FIG. 3 . Specifically, FIG. 3 andFIG. 4 respectively depict a method 300 for generating a sequence 400 ofsummarized routing tables to culminate in an attribute summarized table406 which may be substantially reduced in size from an addresssummarized routing table 404 and/or an un-summarized routing table 402.Each of routing tables 402, 404, and 406 include destination addresses450A associated with respective route information 450B. Routeinformation 450B may include an IP address, microservice identifier,name, or other interface for directing messages towards respectivedestination addresses 450A. Here, route information 450B includes fourinterfaces TI₁-TI₄, which may be associated with multiple destinationaddresses.

In particular, the unsummarized routing table 402 includes a raw listingof all destination addresses received by the route reflector 228. Whilethe unsummarized routing table 402 is discussed in the context of beingreceived by the route reflector 228, it is understood that anycomponent, within the IP network 102 or the network 202, that maintainsa routing table or is configured to manage a routing table can performthe method 300 when it receives or requests BGP routes. Thus, in oneexample where the network 202 does not include a route reflector 228,each component which receives BGP route broadcasts and/or stores thereceived BGP route broadcasts may also perform the method 300 forreducing the size of the routing table.

Routes and/or addresses may be summarized by one or more devices, realor virtual, within the control plane 214. Here, the route reflector 228may summarize addresses received as BGP route broadcasts into routesummaries based on subnet masks included in the received broadcast(operation 302). In general, BGP route addresses can be summarized intoa single routing table entry when each BGP route address has a similarIP address value, mask value, and metadata. As depicted in FIG. 4 , BGProute addresses 408A-B each include similar mask values (e.g., “/24” and“/25”). A mask value represents a count of sequential bits set to “1”that can be applied to an address in a bitwise “AND” operation. Forexample, a mask of 24 represents 24 “1”s in sequence to be applied to anassociated, or “masked”, value. BGP route addresses 408A-B may furtherinclude identical metadata “[1, 2, 3, 4]” which represents a paththrough an autonomous system (“AS”).

Though FIG. 4 depicts metadata including only an AS path, it isunderstood that other metadata may be likewise included and used asdiscussed herein such as, without imputing limitation, a localpreference, an AS path length, a multiple exit discriminator (“MED”),and other data, as will be apparent to a person of ordinary skill in theart. For example, BGP route addresses can further, or instead, besummarized based on a local preference which denotes a preferred entrypoint into a target network. Similarly, a path length, which is a countof the number of paths within a respective AS path, may be used as abasis for summarization. While the AS paths depicted in FIG. 4 eachinclude a path length of “4” (e.g., each AS path metadata includes fourvalues or hops), it is understood that a BGP route broadcast may includelonger paths, shorter paths, or paths of varying length. Likewise, a MEDvalue may be used for summarization purposes and can include a metricassigning a score to each of multiple exits from a first network into asecond another network (e.g., the lower the score, the more preferablethe exit). For sake of clarity, only AS path metadata is depicted anddiscussed below, though it is understood that any and various metadataelements of a BGP route broadcast may be utilized for BGP addresssummarization by attributes as described below.

The BGP route addresses include IP addresses which may be demarcated bymultiple “.” characters interspersed throughout each IP address. Thesedemarcated sections of the IP address are commonly referred to as octetsand each octet may be represented as a binary or decimal number. When inbinary form, each octet includes eight bits each having a value of “1”or “0”. When masked by a mask value, octet values may be preserved ormodified based on the mask value. As depicted in FIG. 4 , BGP routeaddresses 408A-B include IP addresses “192.168.1.128” and “192.168.1.0”which may be respectively converted into binary forms“11000000.10101000.00000001.10000000” and“11000000.10101000.00000001.00000000”. When each respective mask isapplied to each respective IP address of 408A-B, as described below inTable 1, the resultant values (e.g., the masked addresses) differ onlyby the largest bit in the rightmost octet and are thus contiguousaddresses.

TABLE 1 408A: 11000000.10101000.00000001.10000000 192.168.1.128 AND AND11111111.11111111.11111111.00000000 2411000000.10101000.00000001.00000000 192.168.1.011000000.10101000.00000001.00000000 192.168.1.0 AND AND11111111.11111111.11111111.00000000 2411000000.10101000.00000001.00000000 192.168.1.0 408B:11000000.10101000.00000001.10000000 192.168.1.128 AND AND11111111.11111111.11111111.10000000 2511000000.10101000.00000001.10000000 192.168.1.128

Further, BGP route addresses 408A-B include identical metadata “[1, 2,3, 4]” and so may be summarized into an address summarized BGP routeaddress 418 on the address summarized routing table 404. The summarizedBGP route address 418 includes an IP address of “192.168.1.0” and maskvalue of “/24”. In comparison, BGP route addresses 410A-B includecontiguous masked addresses to BGP route addresses 408A-B when maskvalues are applied to respective IP addresses as above. However, BGProute addresses 410A-B each include metadata “[1, 3, 4, 5]” and thuscannot be summarized with BGP route addresses 408A-B and are insteadsummarized into an address summarized route address 420 according to theprocess discussed above. The summarized route address 420 includes themasked address “192.168.1.0” and mask value “/24” along with metadata“[1, 3, 4, 5]”.

As depicted in FIG. 4 , BGP route addresses 412 include IP addresses“219.189.22.5” and “219.189.6.5” along with identical mask values “/24”and metadata “[10, 11, 12, 13]”. Accordingly, the BGP route addresses412 can be summarized as discussed above and entered into the addresssummarized routing table 404 as summarized route address 422. Thesummarized route address 422 includes the masked address“219.189.22.0/22” and masked value “/22” along with metadata “[10, 11,12, 13]”.

In some cases BGP address routes may not be summarizable at this point.BGP address routes 414A-C are examples of such unsummarizable BGPaddress routes. BGP address routes 414A-B include IP addresses and maskvalues which may be contiguous to each other and BGP address routes408A-B. However, BGP address routes 414A-B include respective metadata“[5, 6, 7, 8]” and “[2, 4, 5, 6]”. Likewise, while the BGP broadcastroute 414C would otherwise be contiguous and summarizable with BGPbroadcast routes 412, the included metadata “[1, 2, 8, 9]” causes it tobe unsummarizable. The unsummarizable BGP broadcast routes are enteredinto the address summarized routing table 404 directly as summarizedroute addresses 414 containing substantially identical values to theirunsummarized counterparts (e.g., BGP route addresses 414A-C) on theunsummarized routing table 402.

Having summarized the BGP address routes into the address summarizedrouting table 404, the route reflector 228 may identify and/or sort intoblocks contiguous summarized address routes having similar metadata andidentical mask values (operation 304). As discussed above, addresssummarized routes are contiguous where each route includes identicalvalues in each octet except for the rightmost where either, when inbinary form, the leftmost bit is the only differentiating value or allvalues are identical.

As depicted in FIG. 4 , the address summarized routes 418, 420, 414A,and 414B are contiguous. However, only summarized address routes 418 and420 include identical mask values (e.g., “/24”). Further, the addresssummarized routes 418 and 420 include metadata “[1, 2, 3, 4]” and “[1,3, 4, 5]” respectively. In particular, the route reflector 228 can groupthe contiguous address summarized routes 418 and 420 based on theidentical first value in the respective metadata (e.g., “1”) and/or thefact that the majority of each respective metadata overlaps (e.g., “1”,“3”, and “4” are included in the metadata of both address summarizedroutes).

In comparison, the route reflector 228 will not group the addresssummarized routes 414A-B. While the address summarized routes 414A-B arecontiguous and include identical mask values, the respective metadata ofeach includes different first values (e.g., “5” and “2”) and/or does notinclude majority overlapping metadata. Likewise, address summarizedroutes 422 and 414C are contiguous and each includes the same mask valuebut also each includes altogether different metadata from each other.Accordingly, the route reflector 228 will not group the addresssummarized routes 422 and 414C.

The route reflector 228 may summarize the identified blocks ofcontiguous address summarized routes into attribute summarized routesentered onto the attributed summarized routing table 406 (operation306). In one example, the attribute summarized routes may includeabbreviated or truncated metadata. In other examples, the attributesummarized routes may include other amalgamated forms of the metadata ofthe summarized address routes contributing to each respective entry suchas concatenated metadata, averaged metadata, and the like.

As depicted in FIG. 4 , the route reflector 228 may summarize theaddress summarized routes 418 and 420 as an attribute summarized route430. The attribute summarized route 430 includes the same address andmask value of the address summarized routes 418 and 420 (e.g.,“192.168.1.0” and “/24”). However, the attribute summarized route 430includes only the first shared value of the address summarized routes418 and 420 (e.g., “[1]”).

In comparison, the address summarized routes 414A-C, 420, and 422 areindividually entered into the attribute summarized routing table 406 inrespectively truncated form. The address summarized route 414A is storedin the attribute summarized routing table 406 as an attributedsummarized route 434A including a truncated metadata value of “[5]”. Theaddress summarized route 434B is stored in the attribute summarizedrouting table 406 as an attribute summarized route 434B including atruncated metadata value of “[2]”. The address summarized route 422 isstored in the attribute summarized routing table 406 as an attributesummarized route 432 including a truncated metadata value of “[10]”. Theaddress summarized route 414C is stored in the attribute summarizedrouting table 406 as an attribute summarized route 434C including atruncated metadata value of “[1]”.

Having generated the attribute summarized routing table 406, the routereflector 228 may deploy the attribute summarized routes to the routers205 so they can forward packets across the network 202 accordingly(operation 308). In particular, the routers 205 may each store a copy ofthe attribute summarized routing table 406 in memory. In some examples,the routers 205 may modify the attribute summarized routing table 406into a forwarding table or similar form for rapid use and access. Insome examples, the route reflector 228 may pass the attribute summarizedrouting table 406 to interim devices within the control plane 214 beforethe receipt by the routers 205. The routers 205 may then use theattribute summarized routing table 406, in received or modified form, toforward packets received by the network 202 as depicted in FIG. 1 withregards to routers 105 and IP network 102.

FIG. 5 is a block diagram illustrating an example of a computing deviceor computer system 500 which may be used in implementing the embodimentsof the components of the network disclosed above. For example, thecomputing system 500 of FIG. 5 may be the provider edge device discussedabove. The computer system (system) includes one or more processors502-506. Processors 502-506 may include one or more internal levels ofcache (not shown) and a bus controller or bus interface unit to directinteraction with the processor bus 512. Processor bus 512, also known asthe host bus or the front side bus, may be used to couple the processors502-506 with the system interface 514. System interface 514 may beconnected to the processor bus 512 to interface other components of thesystem 500 with the processor bus 512. For example, system interface 514may include a memory controller 514 for interfacing a main memory 516with the processor bus 512. The main memory 516 typically includes oneor more memory cards and a control circuit (not shown). System interface514 may also include an input/output (I/O) interface 520 to interfaceone or more I/O bridges or I/O devices with the processor bus 512. Oneor more I/O controllers and/or I/O devices may be connected with the I/Obus 526, such as I/O controller 528 and I/O device 540, as illustrated.

I/O device 540 may also include an input device (not shown), such as analphanumeric input device, including alphanumeric and other keys forcommunicating information and/or command selections to the processors502-506. Another type of user input device includes cursor control, suchas a mouse, a trackball, or cursor direction keys for communicatingdirection information and command selections to the processors 502-506and for controlling cursor movement on the display device.

System 500 may include a dynamic storage device, referred to as mainmemory 516, or a random access memory (RAM) or other computer-readabledevices coupled to the processor bus 512 for storing information andinstructions to be executed by the processors 502-506. Main memory 516also may be used for storing temporary variables or other intermediateinformation during execution of instructions by the processors 502-506.System 500 may include a read only memory (ROM) and/or other staticstorage device coupled to the processor bus 512 for storing staticinformation and instructions for the processors 502-506. The system setforth in FIG. 5 is but one possible example of a computer system thatmay employ or be configured in accordance with aspects of the presentdisclosure.

According to one embodiment, the above techniques may be performed bycomputer system 500 in response to processor 504 executing one or moresequences of one or more instructions contained in main memory 516.These instructions may be read into main memory 516 from anothermachine-readable medium, such as a storage device. Execution of thesequences of instructions contained in main memory 516 may causeprocessors 502-506 to perform the process steps described herein. Inalternative embodiments, circuitry may be used in place of or incombination with the software instructions. Thus, embodiments of thepresent disclosure may include both hardware and software components.

A machine readable medium includes any mechanism for storing ortransmitting information in a form (e.g., software, processingapplication) readable by a machine (e.g., a computer). Such media maytake the form of, but is not limited to, non-volatile media and volatilemedia. Non-volatile media includes optical or magnetic disks. Volatilemedia includes dynamic memory, such as main memory 516. Common forms ofmachine-readable medium may include, but is not limited to, magneticstorage medium (e.g., floppy diskette); optical storage medium (e.g.,CD-ROM); magneto-optical storage medium; read only memory (ROM); randomaccess memory (RAM); erasable programmable memory (e.g., EPROM andEEPROM); flash memory; or other types of medium suitable for storingelectronic instructions.

Embodiments of the present disclosure include various steps, which aredescribed in this specification. The steps may be performed by hardwarecomponents or may be embodied in machine-executable instructions, whichmay be used to cause a general-purpose or special-purpose processorprogrammed with the instructions to perform the steps. Alternatively,the steps may be performed by a combination of hardware, software and/orfirmware.

Various modifications and additions can be made to the exemplaryembodiments discussed without departing from the scope of the presentinvention. For example, while the embodiments described above refer toparticular features, the scope of this invention also includesembodiments having different combinations of features and embodimentsthat do not include all of the described features. Accordingly, thescope of the present invention is intended to embrace all suchalternatives, modifications, and variations together with allequivalents thereof.

We claim:
 1. A method for generating a routing table, the method comprising: receiving a plurality of routing information broadcasts, the routing information broadcasts comprising an Internet Protocol (IP) address, a mask value, and metadata; generating an address summarized table between the multiple routing information broadcasts, the address summarized table comprising IP address and corresponding mask values; and generating an attribute summarized table by comparing metadata between address summarized table entries, the attribute summarized table comprising address summarized table entries having identical portions of metadata.
 2. The method of claim 1, wherein the metadata comprises one of a local preference, an autonomous system (AS) path length, an AS path, or a multiple exit discriminator (MED).
 3. The method of claim 1, further comprising forwarding a packet through a network based on the attribute summarized table.
 4. The method of claim 1, wherein generating the attribute summarized table further comprises comparing a respective metadata value of each address summarized table entry and grouping entries having identical metadata values.
 5. The method of claim 4, wherein the routing information broadcasts comprises one or more border gateway protocol (BGP) broadcasts received by one or more route reflectors comprising a data plane for a network.
 6. The method of claim 1, wherein a route reflector receives the routing information broadcasts, and further comprising storing the attribute summarized table on a router.
 7. The method of claim 6, wherein multiple routers store respective copies of the attribute summarized table, each respective copy of the attribute summarized table including interface identifiers for forwarding packets across a network.
 8. The method of claim 1, wherein entries of the attribute summarized table each comprise a summarized address entry associated with a respective interface for forwarding packets.
 9. A system for generating a routing table, the system comprising: one or more processors; and a memory storing instructions to: receive a plurality of routing information broadcasts, the routing information broadcasts comprising an Internet Protocol (IP) address, a mask value, and metadata; generate an address summarized table by comparing IP addresses and mask values between the multiple routing information broadcasts, the address summarized table comprising contiguous IP address and corresponding mask values; and generate an attribute summarized table by comparing metadata between address summarized table entries, the attribute summarized table comprising address summarized table entries having identical portions of metadata.
 10. The system of claim 9, wherein the metadata comprises one of a local preference, an autonomous system (AS) path length, an AS path, or a multiple exit discriminator (MED).
 11. The system of claim 9, wherein the memory stores further instructions to forward a packet based through a network on the attribute summarized table.
 12. The system of claim 9, wherein the routing information broadcasts comprises one or more border gateway protocol (BGP) broadcasts that are received by one or more route reflectors comprising a data plane for a network.
 13. The system of claim 9, wherein entries of the attribute summarized table each comprise a summarized address entry associated with a respective interface for forwarding packets.
 14. The system of claim 9, wherein a route reflector receives the routing information broadcasts, and the memory stores further instructions to store the attribute summarized table on a router.
 15. The method of claim 14, wherein multiple routers store respective copies of the attribute summarized table, each respective copy of the attribute summarized table including interface identifiers for forwarding packets across a network. 